home *** CD-ROM | disk | FTP | other *** search
- Path: news1.h1.usa.pipeline.com!usenet
- From: grantp@usa.pipeline.com(Pete)
- Newsgroups: comp.lang.c++
- Subject: Re: comiling C on Borland C++
- Date: 4 Feb 1996 10:27:53 GMT
- Organization: Kalevi, Inc.
- Message-ID: <4f21n9$kmr@news1.usa.pipeline.com>
- NNTP-Posting-Host: 38.8.60.5
- X-PipeUser: grantp
- X-PipeHub: usa.pipeline.com
- X-PipeGCOS: (Pete)
- X-Newsreader: Pipeline USA v3.3.0
-
- On Feb 04, 1996 05:16:16 in article <comiling C on Borland C++>,
- 'danryoku@leland.Stanford.EDU (Scott Wang)' wrote:
-
-
- >
- > I was trying to use Borland C++ to compile a C program. However
- >when I went to run it I got a linking error. It could not find my
- >#include files.
-
- Actually, it did. You wouldn't have gotten past the compile
- stage if the system failed to find even a single header file.
-
- > Is there a certain dirctory I have to put it in or
- >something. If you have any idea please mail me. Thanks
- >
- The first answer to pop into one's head is that your library
- path isn't correct, but that's unlikely. What is/are the
- linker error message(s)?
-
- --
- Pete Grant
- Kalevi, Inc.
- Object Oriented Software Development
-